home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Tech Arsenal 1
/
Tech Arsenal (Arsenal Computer).ISO
/
tek-06
/
pmail235.zip
/
CHARSET.ZIP
/
CHARSET.TXT
next >
Wrap
Text File
|
1992-09-07
|
4KB
|
106 lines
┌────────────────────────────────────────────────┐
│ Internationalising Pegasus Mail v2.3 (R4). │
└────────────────────────────────────────────────┘
PMail 2.3 (R4) provides some facilities for sites to perform limited
language customizations. The two main areas which can be changed are
PostScript printing of high-bit characters, and the SMTP translation
table PMail uses when sending high-bit characters via the Charon SMTP
gateway. Both alterations are performed using by compiling a source
text file to PMALTEXT.DAT, which is then placed in the same directory
as PMail.exe. The program used to compile the substituted data is
TCOM.EXE, Pegasus Mail's help file compiler, a distant ancestor of
another of my programs, David's Readme Compiler.
1: PostScript
PMail 2.3 (R4) has been modified to print the high bit characters in
the standard IBM character set on PostScript printers. The mapping
PMail uses only works for the standard code page - if you use a
different code page on your system, you'll need to override the
built-in header and prep files.
Examine the file PMALTEXT.SRC supplied in this archive. It consists
of textual sections separated by lines starting with two percentage
signs (%%). The file as supplied has three sections, which perform
the following tasks:
* Section 1 overrides the built-it SMTP translation table.
* Section 2 overrides the PostScript Banner Page PMail prints
* Section 3 overrides the basic PMail PostScript Prep, which
defines the character mappings for high bit characters.
It's not the business of this document to teach you how to program in
PostScript: if you don't feel you know enough PostScript to modify
the Banner and Header sections, then either find someone who does
know enough, or else leave it alone.
Replacing the PostScript Headers is an all-or-nothing job. If you
want to modify section 3, then you must leave section 2 in place,
since PMail uses a straight numeric index into the file to find each
item. If, however, you only want to modify the SMTP table, then the
items after it in the file can be omitted if you wish. Since the
sample file is actually the default items from PMail itself, you can
safely leave any of the sections in place.
Embedded in the PostScript sections are several suspicious-looking
characters - most notably a delete character
/bot { 54 } bind def /top { } bind def
an ASCII vertical bar character
ptsize /|-PC F
and a number of combination characters starting with a tilde
(~u) show
240 504 moveto
(~d) show
240 468 moveto
(~f) show
DO NOT ALTER OR DELETE THESE PLACEHOLDERS!!! They are substituted at
runtime by Pegasus Mail.
2: Altering PMail's SMTP translation table.
Because SMTP is a 7-bit protocol, characters with high bits set
cannot be sent in SMTP messages. PMail attempts to translate high bit
characters to a close equivalent using only 7-bit ASCII. As an
example a u-umlaut 'ü' is actually sent as 'ue' in the message.
Because the built-in SMTP table only works with the standard PC code
page, you may need to alter it if you use a different page.
To modify the SMTP table, use the sample table in PMALTEXT.SRC.
* Locate the character you want to remap
* IMMEDIATELY after it, enter up to 9 characters you want
PMail to print in its place, followed by at least one
space character.
PMail does a machine search through the array of characters for the
one it needs to translate: if it doesn't find it, it prints a space,
otherwise it prints the characters immediately following it until it
hits a space.
Because the table is stored in memory once loaded, you should keep
the number of space delimiters to a minimum.
Compiling PMALTEXT.DAT
To produce PMALTEXT.DAT from your source file, enter this command:
TCOM PMALTEXT.SRC FOO PMALTEXT.DAT
You MUST NOT alter the delimiter lines in the file in any way - the
lines beginning with %%.
-- David Harris --
7 Sep '92.